[libc++] Trigger the BuildKite pipeline from Github Actions #165928
Conversation
Instead of always triggering the BuildKite pipeline and then determining whether there is anything to do, trigger it from the libc++ CI Github action. Since that Github action is only triggered when relevant files have been modified, this simplifies the triggering logic. Importantly, it will also prevent all of the monorepo CI jobs from waiting on the Buildkite pipeline to report that there's nothing to do.
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
ldionne
force-pushed
the
review/trigger-buildkite-via-actions
branch
from
0388383 to
5c0e607
Compare
ldionne
force-pushed
the
review/trigger-buildkite-via-actions
branch
from
0f2e5d3 to
4ba7bc7
Compare
|
Summary of what I tried and found here. I iterated on this in ldionne#6 after creating a copy of the normal libc++ pipeline at https://buildkite.com/llvm-project/ldionne-test-pipeline. The basic issue is that you must disable the automatic Github integration for PRs, otherwise the pipeline gets triggered automatically and you don't get the availability to filter based on modified files. However, once you turn that off, you can trigger a build using the |
1 participant
Instead of always triggering the BuildKite pipeline and then determining whether there is anything to do, trigger it from the libc++ CI Github action. Since that Github action is only triggered when relevant files have been modified, this simplifies the triggering logic.
Importantly, it will also prevent all of the monorepo CI jobs from waiting on the Buildkite pipeline to report that there's nothing to do.